Multiple upstream channel descriptor messages pointing to single upstream channel ID for more efficient operation of a DOCSIS system

ABSTRACT

In a DOCSIS-based communications system, different upstream channel descriptors (UCDs) all identify a single logical upsteam channel identifier (UCID) regardless of the type of cable modem (CM) to which the UCDs are sent. Different CMs having different capabilities (e.g., CMs configured according to the different DOCSIS standards 1.x, 2.0, and 3.0) receive their respective UCDs from an upstream headend. All the UCDs, however, refer to the same logical upstream channel. The different CMs therefore share this single logical upstream channel.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. patent application Ser. No. 11/503,281, filed Aug. 14, 2006, issued as U.S. Pat. No. 7,898,967, which claims the benefit of U.S. Provisional Patent Application No. 60/784,467, filed Mar. 22, 2006, each of which is incorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention described herein relates to communications systems, and more particularly to management of logical channels.

2. Background Art

In systems that follow the Data Over Cable Service Interface Specification (DOCSIS), there is an Upstream Channel Descriptor (UCD) message that is received by cable modems (CMs) in the downstream, i.e., in communications from a headend to a CM. The UCD describes the physical channel parameters of an upstream channel, i.e., a channel used to convey messages from a CM to the headend. The UCD identifies an upstream channel by an Upstream Channel Identifier (UCID) that is unique within a media access control (MAC) domain. A MAC domain is a collection of downstream and upstream channels that is managed under one MAC management entity and that is synchronized under the same timebase. In DOCSIS 1.0, 0.1, and 2.0, after a CM's operation on a particular upstream is determined, the CM only needs to examine UCD messages that contain the UCID of that channel for any changes to the parameters. The CM need not examine messages that have UCIDs for other channels. A change of parameters in the UCD is indicated by an incrementing of the Configuration Change Count in the UCD.

The UCID of the upstream channel also plays a role in the downstream MAP message. A MAP message defines the time and duration of various upstream transmission opportunities on an upstream channel. A MAP message contains a field that has the UCID corresponding to the upstream channel that it is describing. Thus, a CM only needs to look at a MAP message that contains the UCID of the upstream channel that it is using, and need not examine messages that have UCIDs for other channels.

In DOCSIS 2.0, the concept of logical upstream channels was introduced. Multiple logical channels can operate within the same upstream spectrum and are allocated different regions of time in Time Division Multiplex fashion. In particular, DOCSIS 2.0 defined two logical channels to be supported within one physical channel: one logical channel for TDMA transmission and another logical channel for synchronous-code division multiple access (S-CDMA) transmission. Each logical channel is described by its own UCD, and each UCD for a logical channel contains a unique UCID. A CM that operates on one logical channel ignores UCDs for other logical channels that operate in the same spectrum. The CM has no need to understand the existence of other logical channels. The cable modem termination system (CMTS) scheduler keeps track of upstream transmit opportunities that are provided for each of the logical channels as described by the individual MAP messages for each logical channel.

In DOCSIS 3.0, a new type of UCD has been introduced for backwards compatibility reasons. Pre-3.0 DOCSIS cable modems (CMs) will not use this new type of UCD. However, it would be advantageous to be able to support multiple types of CMs, e.g., CMs operating under different communications standards, like DOCSIS 3.0, DOCSIS 2.0, or a version of DOCSIS 1.0 (referred to herein as DOCSIS 1.x) on the same upstream frequency channel without using multiple logical channels. Logical channels can be used for various purposes and therefore allocating them just to separate out 3.0 from 2.0 from 1.x upstream CM communications is not the best use of these logical channels. There is a need, therefore, for a system in which CMs of different types can send upstream communications without having to allocate an upstream logical channel for each CM type.

BRIEF SUMMARY OF THE INVENTION

Different UCDs all identify a single logical upstream channel regardless of the type of CM to which the UCDs are sent. Different CMs having different capabilities (e.g., CMs configured according to the different DOCSIS standards 1.x, 2.0, and 3.0) receive UCDs from a CMTS and preferentially select a UCD with the highest version that is consistent with the DOCSIS version supported by the CM. All the UCDs, however, refer to the same upstream logical channel. The different CMs therefore share this single upstream logical channel.

Compared to the approach described herein, using multiple logical channels to separate DOCSIS 3.0, DOCSIS 2.0, and DOCSIS 1.x CMs that co-exist in the same upstream physical channel consumes more resources, creates more constraints on the scheduler, and results in lost statistical multiplexing gain due to separation of a large bandwidth pipe into several separate smaller pipes. These problems can be circumvented by allowing devices, such as CMs, with different capabilities (as expressed by the different UCDs) to use the same logical channel.

Note that the invention is described herein with respect to cable modems. It should be understood, however, that the invention can operate in conjunction with other types of end-user devices in a system operating under DOCSIS or a similar standard.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

FIG. 1 illustrates the transmission of two different UCD types to CMs operating under two different DOCSIS standards, according to an embodiment of the invention.

FIG. 2 illustrates in greater detail the UCDs of FIG. 1 and the UCID fields therein, according to an embodiment of the invention.

FIG. 3 illustrates the transmission of three different UCD types to CMs operating under three different DOCSIS standards, according to an embodiment of the invention.

FIG. 4 illustrates in greater detail the UCDs of FIG. 3 and the UCID fields therein, according to an embodiment of the invention.

Further embodiments, features, and advantages of the present invention, as well as the operation of the various embodiments of the present invention, are described below with reference to the accompanying drawings.

DETAILED DESCRIPTION OF THE INVENTION

One embodiment of the present invention is now described with reference to the figures, where like reference numbers indicate identical or functionally similar elements. Also in the figures, the leftmost digit of each reference number corresponds to the figure in which the reference number is first used. While specific configurations and arrangements are discussed, it should be understood that this is done for illustrative purposes only. A person skilled in the relevant art will recognize that other configurations and arrangements can be used without departing from the spirit and scope of the invention. It will be apparent to a person skilled in the relevant art that this invention can also be employed in a variety of other systems and applications.

In DOCSIS 3.0, a number of new features and capabilities are specified for the CM and CMTS. The changes that are introduced involve the physical layer, the MAC sublayer, the network layer, security, and network management.

DOCSIS 3.0 also introduces a new type of UCD. In DOCSIS 1.x, a UCD carried a type value of 2 in the MAC Management Message header. In DOCSIS 2.0, another type of UCD was introduced to describe a channel to be used with DOCSIS 2.0 advanced physical layer parameters. The “DOCSIS 2.0 only” UCD carried a type value of 29. In DOCSIS 2.0, a channel with both 1.x and 2.0 physical layer parameters is also described by a UCD of type 2. For DOCSIS 3.0, a new UCD of type 35 is defined. If a CMTS sends a UCD of type 35, any DOCSIS 1.x or 2.0 CM will ignore this UCD since they will not understand the type 35 value. However, 3.0 CMs will be able to interpret the type 35 value.

A type 35 UCD is used in DOCSIS 3.0 to describe an upstream channel in which any of the following DOCSIS 3.0 features are utilized:

1) Burst attributes that enable Selectable Active Codes (SAC) Mode 2 and Code Hopping Mode 2.

2) Burst descriptors corresponding to any of the following Interval Usage Codes (IUCs) 1, 2, 3, 4, 5, 6, 9, 10, and 11.

3) Burst attributes associated with IUC 11 that are not intended for Unsolicted Grant Service (UGS).

DOCSIS 3.0 introduces a physical layer feature that improves ingress noise mitigation when using synchronous-code division multiple access (S-CDMA) in the upstream. With SAC Mode 2, the active codes to be used can be selected from the set of 128 spreading codes. With Code Hopping Mode 2, code hopping is performed only over the active codes that have been selected. DOCSIS 3.0 also introduces the ability of the CMTS to assign burst profiles dynamically to CMs when providing a data grant.Therefore, the type 35 UCD can provide burst profiles corresponding to all the IUCs mentioned above. In addition, DOCSIS 3.0 removes the restriction in DOCSIS 2.0 that IUC 11 has to be associated with UGS grants.

An embodiment of the invention allows a logical channel to be shared among CMs operating under different communications standards, e.g., DOCSIS 3.0 and DOCSIS 2.0 CMs, DOCSIS 3.0 and 1.x CMs, or all three. It is assumed here that logical channels are not used to separate the different CMs with respect to their DOCSIS version support.

First, the case of DOCSIS 2.0 and 3.0 CMs on the same logical upstream channel is discussed. Because certain legacy DOCSIS 2.0 CMs actually check for existence of IUC 5 and 6 in a type 29 UCD and therefore reject such a UCD, a type 29 UCD cannot be used if the intent is to provide one UCD that can be used by 3.0 CMs (which can be assigned any of IUCs 5, 6, 9, 10, and 11 for data), and by 2.0 CMs (that will only use 9, 10, and 11 for data).

Therefore, the embodiment to be discussed involves using two different UCDs that use the same UCID value representing a single logical upstream channel. One UCD is a type 35 UCD that will be ignored by DOCSIS 2.0 CMs, and the other is a type 29 UCD that can be used by DOCSIS 2.0 CMs. The DOCSIS 3.0 CMs will preferentially choose the type 35 UCD over the type 29 UCD per the DOCSIS specifications. Given that the both UCDs point to the same UCID, only one MAP is needed to describe the upstream transmission opportunities on the channel.

This embodiment of the invention is illustrated in FIGS. 1 and 2. In FIG. 1, a CMTS 110 sends two UCDs downstream. UCD 140 is of type 29; UCD 150 is of type 35. These UCDs are received by two CMs operating under two respective communications standards, a DOCSIS 2.0 CM 120, and a DOCSIS 3.0 CM 130. Type 35 UCD 150 will be ignored by CM 120, which will instead accept type 29 UCD 140. CM 130 will choose to accept type 35 UCD 150. FIG. 2 shows both types of UCDs. Type 29 UCD 140 has a UCID field 220, while type 35 UCD 150 has a UCID field 230. Both fields, however, contain references to the same single logical upstream channel UCID_(x).

Now, the case of DOCSIS 1.x, 2.0, and 3.0 CMs on the same logical upstream channel is discussed. The same issue, as discussed before regarding certain legacy DOCSIS 2.0 CMs checking for existence of IUC 5 and 6 in a Type 29 UCD, still applies.

Therefore, multiple UCDs all pointing to the same UCID can be used as a solution in an embodiment of the invention. In this case, there may be two or three UCDs pointing to the same UCID. But with 1.x CMs, there is an additional consideration. To work with current upstream burst receivers, the preamble used for a particular burst profile corresponding to an IUC has to be the same for any CM using the burst profile on the channel. Since DOCSIS 1.x preambles are different than preambles for DOCSIS 2.0 and afterwards, then for a case in which DOCSIS 1.x and DOCSIS 2.0 and 3.0 are sharing the same single logical upstream channel, the preamble type for IUCs 1, 2, 3, 4, 5, and 6 have to be identical.

Therefore, for a channel that is described using multiple UCDs with different types, the UCDs have the following constraints:

-   -   One of the UCDs is of type 35 and the other one can be of type 2         or type 29, or there are three UCDs, where one is of type 35,         one is of type 2 and one is of type 29. The latter case is shown         in FIGS. 3 and 4. A CMTS 310 sends UCDs 335, 340, and 350,         having types 2, 29, and 35 respectively. CM 311 accepts UCD 335         (type 2); CM 320 accepts UCD 340 (type 29); and CM 330 accepts         UCD 350 (type 35). FIG. 4 shows these three UCDs with their         respective UCID fields 410, 420, and 430. All the UCID fields         indicate the same single logical upstream channel, UCID_(y).     -   Burst attributes corresponding to the same IUC are identical in         each of the UCDs in the set.     -   If there is a UCD of type 2 in the set describing the channel,         the burst descriptors for IUC 1, 2, 3, 4, 5, and 6 are type 4         burst descriptors (with DOCSIS 1.x preambles) and the burst         descriptors for IUC 9, 10, and 11 are of type 5 (with DOCSIS 2.0         preambles).     -   If there is a UCD of type 29 and a UCD of type 35 in the set         with no UCD of type 2, the burst descriptors for IUC 1, 2, 3, 5,         6, 9, 10, and 11 are of type 5.

This invention would not be restricted to necessarily just two or three UCDs mapped to one UCID. A future version of DOCSIS could introduce another UCD type, and then there could be more than three UCDs mapped to one UCID.

While some embodiments of the present invention have been described above, it should be understood that it has been presented by way of examples only and not meant to limit the invention. It will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. Thus, the breadth and scope of the present invention should not be limited by the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. 

What is claimed is:
 1. An apparatus for allocating a single logical upstream channel to a plurality of end user devices, comprising: a central controller configured to send a plurality of upstream channel descriptors (UCDs) identifying the single logical upstream channel to the plurality of end user devices, the single logical upstream channel being from among a plurality of logical upstream channels within a single physical channel, wherein each UCD from among the plurality of UCDs is characterized as having a different UCD numerical type field value from among a plurality of UCD numerical type field values.
 2. The apparatus of claim 1, wherein each end user device from among the plurality of end user devices is configured to operate in accordance with a corresponding communication standard from among a plurality of communications standards.
 3. The apparatus of claim 1, wherein each UCD from among the plurality of UCDs includes an upstream channel identifier (UCID) that identifies the single logical upstream channel.
 4. The apparatus of claim 1, wherein the plurality of UCD numerical type field values are Data Over Cable Interface Standard (DOCSIS) message type values.
 5. The apparatus of claim 1, wherein the plurality of UCD numerical type field values comprise: a first UCD numerical type field value corresponding to a version of Data Over Cable Interface Standard (DOCSIS) 1; a second UCD numerical type field value corresponding to a version of DOCSIS 2; and a third UCD numerical type field value corresponding to a version of DOCSIS 3, wherein the first UCD numerical type field value, the second UCD numerical type field value, and the third UCD numerical type field value are different from each other.
 6. The apparatus of claim 5, wherein the first UCD numerical type field value is 2, wherein the second UCD numerical type field value is 29, and wherein the third UCD numerical type field value is
 35. 7. The apparatus of claim 1, wherein the plurality of UCD numerical type field values comprise: a first UCD numerical type field value corresponding to a version of Data Over Cable Interface Standard (DOCSIS) 1; and a second UCD numerical type field value corresponding to a version of DOCSIS 2, wherein the first UCD numerical type field value and the second UCD numerical type field value are different from each other.
 8. The apparatus of claim 7, wherein the first UCD numerical type field value is 2, and wherein the second UCD numerical type field value is
 29. 9. The apparatus of claim 1, wherein the plurality of UCD numerical type field values comprise: a first UCD numerical type field value corresponding to a version of Data Over Cable Interface Standard (DOCSIS) 1; and a second UCD numerical type field value corresponding to a version of DOCSIS 3, wherein the first UCD numerical type field value and the second UCD numerical type field value are different from each other.
 10. The apparatus of claim 9, wherein the first UCD numerical type field value is 2, and wherein the second UCD numerical type field value is
 35. 11. The apparatus of claim 1, wherein the plurality of UCD numerical type field values comprise: a first UCD numerical type field value corresponding to a version of Data Over Cable Interface Standard (DOCSIS) 2; and a second UCD numerical type field value corresponding to a version of DOCSIS 3, wherein the first UCD numerical type field value and the second UCD numerical type field value are different from each other.
 12. The apparatus of claim 11, wherein the first UCD numerical type field value is 29, and wherein the second UCD numerical type field value is
 35. 13. The apparatus of claim 1, wherein the plurality of numerical type values include: a Data Over Cable Interface Standard (DOCSIS) UCD numerical type field value of 2; a DOCSIS UCD numerical type field value of 29; or a DOCSIS UCD numerical type field value of
 35. 14. The apparatus of claim 1, wherein an end user device from among the plurality of end user devices is a cable modem.
 15. The apparatus of claim 1, wherein the central controller is a cable modem termination system.
 16. An apparatus for allocating a single logical upstream channel to a plurality of end user devices, comprising: a central controller configured to send a plurality of upstream channel descriptors (UCDs) identifying the single logical upstream channel to the plurality of end user devices, the single logical upstream channel being from among a plurality of logical upstream channels within a single physical channel, wherein each UCD from among the plurality of UCDs is characterized as having a different Data Over Cable Interface Standard (DOCSIS) UCD message type field value from among a plurality of DOCSIS UCD message type field values.
 17. The apparatus of claim 16, wherein each end user device from among the plurality of end user devices is configured to operate in accordance with a corresponding DOCSIS communication standard from among a plurality of DOCSIS communications standards.
 18. The apparatus of claim 16, wherein each UCD from among the plurality of UCDs includes an upstream channel identifier (UCID) that identifies the single logical upstream channel.
 19. The apparatus of claim 16, wherein the plurality of DOCSIS UCD message type field values comprise: a first UCD message type field value corresponding to a version of Data Over Cable Interface Standard (DOCSIS) 1; a second UCD message type field value corresponding to a version of DOCSIS 2; and a third UCD message type field value corresponding to a version of DOCSIS 3, wherein the first UCD message type field value, the second UCD message type field value, and the third UCD message type field value are different from each other.
 20. The apparatus of claim 19, wherein the first UCD message type field value is 2, wherein the second UCD message type field value is 29, and wherein the third UCD message type field value is
 35. 21. The apparatus of claim 16, wherein the plurality of DOCSIS UCD message type field values comprise: a first DOCSIS UCD message type field value corresponding to a version of DOCSIS 1; and a second DOCSIS UCD message type field value corresponding to a version of DOCSIS 2, wherein the first DOCSIS UCD message type field value and the second DOCSIS UCD message type field value are different from each other.
 22. The apparatus of claim 21, wherein the first DOCSIS UCD message type field value is 2, and wherein the second DOCSIS UCD message type field value is
 29. 23. The apparatus of claim 16, wherein the plurality of DOCSIS UCD message type field values comprise: a first DOCSIS UCD message type field value corresponding to a version of Data Over Cable Interface Standard (DOCSIS) 1; and a second DOCSIS UCD message type field value corresponding to a version of DOCSIS 3, wherein the first DOCSIS UCD message type field value and the second DOCSIS UCD message type field value are different from each other.
 24. The apparatus of claim 23, wherein the first DOCSIS UCD message type field value is 2, and wherein the second DOCSIS UCD message type field value is
 35. 25. The apparatus of claim 16, wherein the plurality of DOCSIS UCD message type field values comprise: a first DOCSIS UCD message type field value corresponding to a version of DOCSIS 2; and a second DOCSIS UCD message type field value corresponding to a version of DOCSIS 3, wherein the first DOCSIS UCD message type field value and the second DOCSIS UCD message type field value are different from each other.
 26. The apparatus of claim 25, wherein the first DOCSIS UCD message type field value is 29, and wherein the second DOCSIS UCD message type field value is
 35. 27. The apparatus of claim 16, wherein the plurality of DOCSIS UCD message type field values include: a DOCSIS UCD message type field value of 2; a DOCSIS UCD message type field value of 29; or a DOCSIS UCD message type field value of
 35. 28. The apparatus of claim 16, wherein an end user device from among the plurality of end user devices is a cable modem.
 29. The apparatus of claim 16, wherein the central controller is a cable modem termination system. 